The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Build applications using the provided language utilities
|
|
Review the program requirements Completed |
Evidence:
|
Divide multiple source-code files into logical units and packages Completed |
Evidence:
|
Use at least two of the utilities of the target language, allowing for the internal storage of collections of data Completed |
Evidence:
|
Use the utilities of the target language, providing internal data-sorting and searching facilities Completed |
Evidence:
|
Employ integrated-development environment facilities, to make files to automate program building Completed |
Evidence:
|
Follow the guidelines for developing maintainable code, adhering to coding standards Completed |
Evidence:
|
Use the facilities in the language for persisting objects to binary files Completed |
Evidence:
|
Use the operator and function or method overloading facilities available in the language, at an introductory level Completed |
Evidence:
|
Use exception-handling techniques to ensure program stability Completed |
Evidence:
|
Use of a class that is based on multiple inheritances Completed |
Evidence:
|
Write programs that interact with a database
|
|
Design and implement programs that connect to a database Completed |
Evidence:
|
Design and implement programs that use the language facilities to extract, update, and delete data stored in a database Completed |
Evidence:
|
Design and implement programs that use the language facilities to manipulate database structure (query, create and delete) Completed |
Evidence:
|
Write programs that deliver transactional integrity Completed |
Evidence:
|
Write the graphical user interface
|
|
Employ the graphical user interface (GUI) framework, or text windowing interface, appropriate to the chosen language Completed |
Evidence:
|
Use standard GUI components Completed |
Evidence:
|
Use the facilities within the language for GUI objects to respond to user and program-generated events Completed |
Evidence:
|
Debug the application
|
|
Use stand-alone debugging tools, or tools provided by the integrated development environment, to examine variables, and trace the running code Completed |
Evidence:
|
Use the debugger to detect logical and coding errors Completed |
Evidence:
|
Use the tracing of code and examination of variable contents during execution, to detect and correct errors Completed |
Evidence:
|
Test the application
|
|
Design and document limited tests of code Completed |
Evidence:
|
Undertake limited testing of the produced code to ensure that it complies with the program specification Completed |
Evidence:
|
Capture and document the test results Completed |
Evidence:
|
Create and maintain documentation
|
|
Read and interpret the supplied design document, to create the code Completed |
Evidence:
|
Create and maintain program documentation Completed |
Evidence:
|